Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3846fc5af70d7ebc23aac6dd0caa83fdf56a855845df979b11aafc410745cf70

Tx prefix hash: e2651c5ee9637a2901f973a5afd1e7279a7216ff1247a5da9db0179f3f292a89
Tx public key: 0f1d36a43efe059226fa4332bd747e5b353e9b28edf3a78a163f914412ab42db
Timestamp: 1721930378 Timestamp [UCT]: 2024-07-25 17:59:38 Age [y:d:h:m:s]: 00:121:19:41:53
Block: 1073554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87168 RingCT/type: yes/0
Extra: 010f1d36a43efe059226fa4332bd747e5b353e9b28edf3a78a163f914412ab42db02110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6687b2e6a60fb3c7e9bdef1d053df60cc18ca45bc025e18fef2d6aefd6bf2e9f 0.600000000000 1546057 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": 1073564, "vin": [ { "gen": { "height": 1073554 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6687b2e6a60fb3c7e9bdef1d053df60cc18ca45bc025e18fef2d6aefd6bf2e9f" } } ], "extra": [ 1, 15, 29, 54, 164, 62, 254, 5, 146, 38, 250, 67, 50, 189, 116, 126, 91, 53, 62, 155, 40, 237, 243, 167, 138, 22, 63, 145, 68, 18, 171, 66, 219, 2, 17, 0, 0, 0, 12, 233, 20, 221, 21, 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