Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8888c7940b5e514b1970e2c816b76283b32ec5e6164510d4ae1d30e3568a3156

Tx prefix hash: 5f8c1c8b31134521de1500530e5694c6aa15d9b9c03a4057d765c4410500f3e5
Tx public key: 2a11f72bd8e257a860ba862dc55fe1be83151976078d553042fc602cc9d66dcc
Timestamp: 1731405074 Timestamp [UCT]: 2024-11-12 09:51:14 Age [y:d:h:m:s]: 00:155:03:17:42
Block: 1152015 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110712 RingCT/type: yes/0
Extra: 012a11f72bd8e257a860ba862dc55fe1be83151976078d553042fc602cc9d66dcc021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c1e56f33e94727fef475d0f25a8a6d0803054200fcdc15a289ab37e78894aa5 0.600000000000 1637606 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": 1152025, "vin": [ { "gen": { "height": 1152015 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c1e56f33e94727fef475d0f25a8a6d0803054200fcdc15a289ab37e78894aa5" } } ], "extra": [ 1, 42, 17, 247, 43, 216, 226, 87, 168, 96, 186, 134, 45, 197, 95, 225, 190, 131, 21, 25, 118, 7, 141, 85, 48, 66, 252, 96, 44, 201, 214, 109, 204, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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