Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3848798d9fdf7ea1792857cfa21f4e47051cf1d368c5b7c53a75a949e933ef47

Tx prefix hash: 9a5df6727a0d5824eb852790d743bb4c80d80bae3ab607b860f7cdf3573da952
Tx public key: ca40c0f50230ab5e85dada9c049ed7a1f1f2cf426148ff3bc77af68aa7557c6c
Timestamp: 1670356594 Timestamp [UCT]: 2022-12-06 19:56:34 Age [y:d:h:m:s]: 02:176:14:07:06
Block: 646888 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 647951 RingCT/type: yes/0
Extra: 01ca40c0f50230ab5e85dada9c049ed7a1f1f2cf426148ff3bc77af68aa7557c6c02110000000e75e3f0e9000000000000000000

1 output(s) for total of 4.411553101000 dcy

stealth address amount amount idx
00: 02120a836c965888d4f250ffba47802e591555247b40fa235f3ce69a0c0f4dff 4.411553101000 1087129 of 0

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": 646898, "vin": [ { "gen": { "height": 646888 } } ], "vout": [ { "amount": 4411553101, "target": { "key": "02120a836c965888d4f250ffba47802e591555247b40fa235f3ce69a0c0f4dff" } } ], "extra": [ 1, 202, 64, 192, 245, 2, 48, 171, 94, 133, 218, 218, 156, 4, 158, 215, 161, 241, 242, 207, 66, 97, 72, 255, 59, 199, 122, 246, 138, 167, 85, 124, 108, 2, 17, 0, 0, 0, 14, 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