Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3f67e16571175a0d1bb79e69c85ae0b05c072a2035b94c51308c32365142b5d

Tx prefix hash: 7396019f9995948768d075e9a09981137bc3c8ef23e0727de7e238c2c7d8faac
Tx public key: 427d47ef8b4598e3e1430b3d4a21a45847c0aebe8123d67ac503ae193288bc52
Timestamp: 1702903895 Timestamp [UCT]: 2023-12-18 12:51:35 Age [y:d:h:m:s]: 01:146:23:34:08
Block: 915818 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366200 RingCT/type: yes/0
Extra: 01427d47ef8b4598e3e1430b3d4a21a45847c0aebe8123d67ac503ae193288bc5202110000000975e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1217e2ecefd871be07da60ef96d8c7760eb06982703cd7313cfc60c9f6bad47 0.600000000000 1373252 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": 915828, "vin": [ { "gen": { "height": 915818 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1217e2ecefd871be07da60ef96d8c7760eb06982703cd7313cfc60c9f6bad47" } } ], "extra": [ 1, 66, 125, 71, 239, 139, 69, 152, 227, 225, 67, 11, 61, 74, 33, 164, 88, 71, 192, 174, 190, 129, 35, 214, 122, 197, 3, 174, 25, 50, 136, 188, 82, 2, 17, 0, 0, 0, 9, 117, 227, 240, 233, 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