Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c19d187da0d2e4a412fea835253b559303c6e2e57ce8c44e1fde9ed4de410fd

Tx prefix hash: 655e6bc4452fb3593f195bfbe0a478e5a215c853ff0ede2a20a9a60edfaeb437
Tx public key: 15e52fbf2500d8b54e3d5586f56517d0bf796da3cfe51bfb30d04e969e33684f
Timestamp: 1705371969 Timestamp [UCT]: 2024-01-16 02:26:09 Age [y:d:h:m:s]: 01:044:01:12:16
Block: 936255 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292558 RingCT/type: yes/0
Extra: 0115e52fbf2500d8b54e3d5586f56517d0bf796da3cfe51bfb30d04e969e33684f02110000000379bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a60ca2ded6d32e687b12d6442b87c110df99b5fc4a12e0c1934f04dc1f1a9e7 0.600000000000 1394279 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": 936265, "vin": [ { "gen": { "height": 936255 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a60ca2ded6d32e687b12d6442b87c110df99b5fc4a12e0c1934f04dc1f1a9e7" } } ], "extra": [ 1, 21, 229, 47, 191, 37, 0, 216, 181, 78, 61, 85, 134, 245, 101, 23, 208, 191, 121, 109, 163, 207, 229, 27, 251, 48, 208, 78, 150, 158, 51, 104, 79, 2, 17, 0, 0, 0, 3, 121, 189, 163, 190, 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