Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57e84fee14718aad3b14cae347365f3e23563ad68e03581a3f767d7809d2a7b4

Tx prefix hash: cedfbf8c7221342e8c9a494be95880f7ddc3e33af7d8eb5deb5e10b5e9553cc0
Tx public key: f116578a3404c95ddb24b1a697149b5cd6ec923e2e16fc7a6470300aae200999
Timestamp: 1733859460 Timestamp [UCT]: 2024-12-10 19:37:40 Age [y:d:h:m:s]: 01:013:00:32:56
Block: 1172369 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267718 RingCT/type: yes/0
Extra: 01f116578a3404c95ddb24b1a697149b5cd6ec923e2e16fc7a6470300aae2009990211000000016e963a0b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5501457b629cbe7d3f15e18b2dc4ef928ae1537f6c17b67a7214dc0ecf5e458 0.600000000000 1658252 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": 1172379, "vin": [ { "gen": { "height": 1172369 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5501457b629cbe7d3f15e18b2dc4ef928ae1537f6c17b67a7214dc0ecf5e458" } } ], "extra": [ 1, 241, 22, 87, 138, 52, 4, 201, 93, 219, 36, 177, 166, 151, 20, 155, 92, 214, 236, 146, 62, 46, 22, 252, 122, 100, 112, 48, 10, 174, 32, 9, 153, 2, 17, 0, 0, 0, 1, 110, 150, 58, 11, 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