Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45135dfd6ae5db494333b806fec176ce083d5dcc4a228d937cc4295d52d6b4fd

Tx prefix hash: a0d5008e2a64b0155cfc1bb8bfa3ef3394d76547f47c813679530065c8f45d49
Tx public key: ae5b1f657c7a8e554eb750a8ec152acfba979a4799b64edc98b6133179b2627a
Timestamp: 1722836544 Timestamp [UCT]: 2024-08-05 05:42:24 Age [y:d:h:m:s]: 00:111:13:37:33
Block: 1081063 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79828 RingCT/type: yes/0
Extra: 01ae5b1f657c7a8e554eb750a8ec152acfba979a4799b64edc98b6133179b2627a02110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36fc6a9d6655c87bfdc8d291968abd8c4d36f97e9c72fc5f6db8c91a1e6915b9 0.600000000000 1554664 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": 1081073, "vin": [ { "gen": { "height": 1081063 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36fc6a9d6655c87bfdc8d291968abd8c4d36f97e9c72fc5f6db8c91a1e6915b9" } } ], "extra": [ 1, 174, 91, 31, 101, 124, 122, 142, 85, 78, 183, 80, 168, 236, 21, 42, 207, 186, 151, 154, 71, 153, 182, 78, 220, 152, 182, 19, 49, 121, 178, 98, 122, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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