Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f920b1d8de3a39acaaa4ce57212c8c7fbede9312be6c6cf0e5edf0cd92777fed

Tx prefix hash: cf2fa62bad056b2c38afd4cb7a65c72e9ee824713d0d50fdd2bc040f18c9b90f
Tx public key: 70c155181636a711461396fa9e4b5f5846dc7779113146064ffd66a2d52e774b
Timestamp: 1714234767 Timestamp [UCT]: 2024-04-27 16:19:27 Age [y:d:h:m:s]: 00:199:17:53:39
Block: 1009752 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142996 RingCT/type: yes/0
Extra: 0170c155181636a711461396fa9e4b5f5846dc7779113146064ffd66a2d52e774b0211000000117a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 622fdb40f66e4861c055fe659e51281a788b9d8a63d28b3fdc68f328d1610e3b 0.600000000000 1471512 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": 1009762, "vin": [ { "gen": { "height": 1009752 } } ], "vout": [ { "amount": 600000000, "target": { "key": "622fdb40f66e4861c055fe659e51281a788b9d8a63d28b3fdc68f328d1610e3b" } } ], "extra": [ 1, 112, 193, 85, 24, 22, 54, 167, 17, 70, 19, 150, 250, 158, 75, 95, 88, 70, 220, 119, 121, 17, 49, 70, 6, 79, 253, 102, 162, 213, 46, 119, 75, 2, 17, 0, 0, 0, 17, 122, 156, 244, 199, 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