Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e595c026be74bcd126c3f0fef31b4e319c844adf10d0112b498527b91fbf9b51

Tx prefix hash: 3e252aa59da3505c78ff943e19950859f60453c5e37f75f8c7a45ddbb9449a4d
Tx public key: 3fd3ccb4e884e271f3d642d65c33c073cd4c7929267d66c5668f72bad44be900
Timestamp: 1625654348 Timestamp [UCT]: 2021-07-07 10:39:08 Age [y:d:h:m:s]: 03:211:03:25:07
Block: 289660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 920875 RingCT/type: yes/0
Extra: 013fd3ccb4e884e271f3d642d65c33c073cd4c7929267d66c5668f72bad44be900021100000097694a138f000000000000000000

1 output(s) for total of 67.335521544000 dcy

stealth address amount amount idx
00: deadf44f0c33ea83e0e3764db675cac4266ec617e8b7955b7960e726512b1409 67.335521544000 606720 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": 289670, "vin": [ { "gen": { "height": 289660 } } ], "vout": [ { "amount": 67335521544, "target": { "key": "deadf44f0c33ea83e0e3764db675cac4266ec617e8b7955b7960e726512b1409" } } ], "extra": [ 1, 63, 211, 204, 180, 232, 132, 226, 113, 243, 214, 66, 214, 92, 51, 192, 115, 205, 76, 121, 41, 38, 125, 102, 197, 102, 143, 114, 186, 212, 75, 233, 0, 2, 17, 0, 0, 0, 151, 105, 74, 19, 143, 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