Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 172d03236958f54642bc6e3c589fe60b5df2e5837e6d10cb630cad68ad60c746

Tx prefix hash: 1716e7d7a127d0d378dace44660d3a0ff3b1b81227985349e67114d3641d2bab
Tx public key: 265477ee9a9d7ef29e292277d229297b8fb977eda1c07e63fc0cd21aa1820a62
Timestamp: 1636054308 Timestamp [UCT]: 2021-11-04 19:31:48 Age [y:d:h:m:s]: 03:130:19:52:34
Block: 367380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 871826 RingCT/type: yes/0
Extra: 01265477ee9a9d7ef29e292277d229297b8fb977eda1c07e63fc0cd21aa1820a620211000000094a0f5013000000000000000000

1 output(s) for total of 37.214993839000 dcy

stealth address amount amount idx
00: 7ee0a416265e4105e1c5e5eec69612a5eb5c8bae9ca9514f0ea8f12ad19d3df5 37.214993839000 745460 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": 367390, "vin": [ { "gen": { "height": 367380 } } ], "vout": [ { "amount": 37214993839, "target": { "key": "7ee0a416265e4105e1c5e5eec69612a5eb5c8bae9ca9514f0ea8f12ad19d3df5" } } ], "extra": [ 1, 38, 84, 119, 238, 154, 157, 126, 242, 158, 41, 34, 119, 210, 41, 41, 123, 143, 185, 119, 237, 161, 192, 126, 99, 252, 12, 210, 26, 161, 130, 10, 98, 2, 17, 0, 0, 0, 9, 74, 15, 80, 19, 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