Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0fcef42d1b81e157783e8c0597b4555c286d4dde2db99587a11da54d1ecc1f7

Tx prefix hash: eee5f44b66c6e86e74d198298711ab6f1e8f91aabccb30f0fabfad4839c71977
Tx public key: b440a1454c668d0f394fc2a05c9c0005462cfd1ccb8bca33f87a9ffd82d3b525
Timestamp: 1705412824 Timestamp [UCT]: 2024-01-16 13:47:04 Age [y:d:h:m:s]: 01:089:03:36:35
Block: 936600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324825 RingCT/type: yes/0
Extra: 01b440a1454c668d0f394fc2a05c9c0005462cfd1ccb8bca33f87a9ffd82d3b5250211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c1074f5ab9ca2be35c9b978629100ae4aaa43dc4ae90c1b06f6e4622b60193c 0.600000000000 1394634 of 15

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": 936610, "vin": [ { "gen": { "height": 936600 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c1074f5ab9ca2be35c9b978629100ae4aaa43dc4ae90c1b06f6e4622b60193c" } } ], "extra": [ 1, 180, 64, 161, 69, 76, 102, 141, 15, 57, 79, 194, 160, 92, 156, 0, 5, 70, 44, 253, 28, 203, 139, 202, 51, 248, 122, 159, 253, 130, 211, 181, 37, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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