Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 48cc1728a7f89891fdb084c2e0382803e8ebb79da302e8b4b57a76291a04c8ce

Tx prefix hash: e3ec5dfda127ad7863785057202288257e89eac01b13f7fc8a6174477b16e36c
Tx public key: 807f6c1ea3c2ad9b05e58aca88cb7595554ca080356384ca5fae0169f81e89a5
Timestamp: 1638918672 Timestamp [UCT]: 2021-12-07 23:11:12 Age [y:d:h:m:s]: 02:353:10:43:52
Block: 390661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 770666 RingCT/type: yes/0
Extra: 01807f6c1ea3c2ad9b05e58aca88cb7595554ca080356384ca5fae0169f81e89a502110000001c379224c2000000000000000000

1 output(s) for total of 31.160046190000 dcy

stealth address amount amount idx
00: a0beb5422931ad0a5bf7e624869eee089ee3b91e72b0146b2e8f9ee0ce7c5be7 31.160046190000 786568 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 390671, "vin": [ { "gen": { "height": 390661 } } ], "vout": [ { "amount": 31160046190, "target": { "key": "a0beb5422931ad0a5bf7e624869eee089ee3b91e72b0146b2e8f9ee0ce7c5be7" } } ], "extra": [ 1, 128, 127, 108, 30, 163, 194, 173, 155, 5, 229, 138, 202, 136, 203, 117, 149, 85, 76, 160, 128, 53, 99, 132, 202, 95, 174, 1, 105, 248, 30, 137, 165, 2, 17, 0, 0, 0, 28, 55, 146, 36, 194, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8