Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6bbae64424a51573b195887d729bef2192636ad0d8953a1589cb440d30807058

Tx prefix hash: 2e41a98a82a94a0aac9029acd05a70a4849b2de8ff6317d017d1fa5d829732cd
Tx public key: 48b20cb5b0bf642a0873861662e5e7687c8cb00afaef1a694c4d58545c251758
Timestamp: 1694988033 Timestamp [UCT]: 2023-09-17 22:00:33 Age [y:d:h:m:s]: 01:128:04:25:06
Block: 850381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352882 RingCT/type: yes/0
Extra: 0148b20cb5b0bf642a0873861662e5e7687c8cb00afaef1a694c4d58545c25175802110000000133af99f4000000000000000000

1 output(s) for total of 0.933974014000 dcy

stealth address amount amount idx
00: 11d6d4ce311372f3e9e8f014ae485ca86e8b093ff5c95bcd370d1f9731fa04d1 0.933974014000 1304097 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": 850391, "vin": [ { "gen": { "height": 850381 } } ], "vout": [ { "amount": 933974014, "target": { "key": "11d6d4ce311372f3e9e8f014ae485ca86e8b093ff5c95bcd370d1f9731fa04d1" } } ], "extra": [ 1, 72, 178, 12, 181, 176, 191, 100, 42, 8, 115, 134, 22, 98, 229, 231, 104, 124, 140, 176, 10, 250, 239, 26, 105, 76, 77, 88, 84, 92, 37, 23, 88, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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