Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db257f18aa3821af3058e890475e22a9233db83b12a72341758267871272b969

Tx prefix hash: cf411cfec7ce7e8a17dc0f1345eb3c1f54fe6ef8df3cbe05ea6a91fe8f0c4c2d
Tx public key: 404da212e2e9faa823150208330676539d7f34593622b584c6076e8bdd244cc0
Timestamp: 1644628659 Timestamp [UCT]: 2022-02-12 01:17:39 Age [y:d:h:m:s]: 02:293:02:33:44
Block: 436668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 728774 RingCT/type: yes/0
Extra: 01404da212e2e9faa823150208330676539d7f34593622b584c6076e8bdd244cc0021100000010bf7ee4e7000000000000000000

1 output(s) for total of 21.935015458000 dcy

stealth address amount amount idx
00: 42b2262e287bbdac0e3ffccdae700bcf751a9fd5c4d218727322e698155186f2 21.935015458000 848091 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": 436678, "vin": [ { "gen": { "height": 436668 } } ], "vout": [ { "amount": 21935015458, "target": { "key": "42b2262e287bbdac0e3ffccdae700bcf751a9fd5c4d218727322e698155186f2" } } ], "extra": [ 1, 64, 77, 162, 18, 226, 233, 250, 168, 35, 21, 2, 8, 51, 6, 118, 83, 157, 127, 52, 89, 54, 34, 181, 132, 198, 7, 110, 139, 221, 36, 76, 192, 2, 17, 0, 0, 0, 16, 191, 126, 228, 231, 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