Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36611321fdf792a1511eb92886510763f9b04ce33eca4a6e4343fd2437cf617d

Tx prefix hash: 07b35bbb8aba2ad53f8bf13b2dd107806502dc1ff234ec2a342fc38b4a6d86e3
Tx public key: 0752297415327b0e3ff8f77a09d6b1b6a1a6e1b6d0ade82bf0dbb4f1be6f3ae5
Timestamp: 1729079994 Timestamp [UCT]: 2024-10-16 11:59:54 Age [y:d:h:m:s]: 01:024:00:53:41
Block: 1132853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275522 RingCT/type: yes/0
Extra: 010752297415327b0e3ff8f77a09d6b1b6a1a6e1b6d0ade82bf0dbb4f1be6f3ae5021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0604f00c86d30e175dbca4fdb0492380a5d4e16d5af57862874b5d8e1bb884a9 0.600000000000 1615866 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": 1132863, "vin": [ { "gen": { "height": 1132853 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0604f00c86d30e175dbca4fdb0492380a5d4e16d5af57862874b5d8e1bb884a9" } } ], "extra": [ 1, 7, 82, 41, 116, 21, 50, 123, 14, 63, 248, 247, 122, 9, 214, 177, 182, 161, 166, 225, 182, 208, 173, 232, 43, 240, 219, 180, 241, 190, 111, 58, 229, 2, 17, 0, 0, 0, 3, 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