Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03d946bf9e3a1924452fe1f38ef2ba260bb86d3fe0b519bc5a4be049bb50322b

Tx prefix hash: 438acae395261dcadc957b194b2cbf328e786e92c8a3fe5c9fe2b75c2396c7f7
Tx public key: 08eb1a682cd696bd5208a531065596c268ec0a3be0f6a28cb145a9627073a726
Timestamp: 1728672802 Timestamp [UCT]: 2024-10-11 18:53:22 Age [y:d:h:m:s]: 00:174:05:29:38
Block: 1129460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124307 RingCT/type: yes/0
Extra: 0108eb1a682cd696bd5208a531065596c268ec0a3be0f6a28cb145a9627073a72602110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c31734b2c10b52f41b4f51a8967fd6b18fbaae01cabb26aad8d770de96044d2 0.600000000000 1612287 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": 1129470, "vin": [ { "gen": { "height": 1129460 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c31734b2c10b52f41b4f51a8967fd6b18fbaae01cabb26aad8d770de96044d2" } } ], "extra": [ 1, 8, 235, 26, 104, 44, 214, 150, 189, 82, 8, 165, 49, 6, 85, 150, 194, 104, 236, 10, 59, 224, 246, 162, 140, 177, 69, 169, 98, 112, 115, 167, 38, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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