Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d2ce5f6b34747f8406b162f84794e9b5a4020450ac0cf96f4d175eec9311be0

Tx prefix hash: 41c032c690f6804426d8a87506782d87fbd72e859d40c7b5b30b8f3d1de4bbfe
Tx public key: dcf1664cfc5e54697bf3a4e88c4aa8f31a1adadce76b3c8909d50a1d019c95f8
Timestamp: 1636204212 Timestamp [UCT]: 2021-11-06 13:10:12 Age [y:d:h:m:s]: 03:129:02:48:48
Block: 368593 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 870637 RingCT/type: yes/0
Extra: 01dcf1664cfc5e54697bf3a4e88c4aa8f31a1adadce76b3c8909d50a1d019c95f8021100000009a272b9cb000000000000000000

1 output(s) for total of 36.872176764000 dcy

stealth address amount amount idx
00: ea1b334143cec022c552ba0e5b1e30a4279c9a909ec5421f9d8b849dceec8623 36.872176764000 747577 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": 368603, "vin": [ { "gen": { "height": 368593 } } ], "vout": [ { "amount": 36872176764, "target": { "key": "ea1b334143cec022c552ba0e5b1e30a4279c9a909ec5421f9d8b849dceec8623" } } ], "extra": [ 1, 220, 241, 102, 76, 252, 94, 84, 105, 123, 243, 164, 232, 140, 74, 168, 243, 26, 26, 218, 220, 231, 107, 60, 137, 9, 213, 10, 29, 1, 156, 149, 248, 2, 17, 0, 0, 0, 9, 162, 114, 185, 203, 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