Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d72aace584e38dd32f57051a23ae1c7d6f5d30caf3d403fd3906fa4c80a60d19

Tx prefix hash: 196c421e0bbb05f2f8b6727f7a6d9af5244226950e65c53496093f86a68b0f1e
Tx public key: 3a979165a14c05b8e843868cbed9baa036d4417201acbd1033b4b310987aa295
Timestamp: 1718152172 Timestamp [UCT]: 2024-06-12 00:29:32 Age [y:d:h:m:s]: 01:150:15:39:54
Block: 1042241 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366235 RingCT/type: yes/0
Extra: 013a979165a14c05b8e843868cbed9baa036d4417201acbd1033b4b310987aa29502110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9bd621802f9fdfa9933faed563c5b291e4ef4536ce8732732e93288157b260b9 0.600000000000 1511112 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": 1042251, "vin": [ { "gen": { "height": 1042241 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9bd621802f9fdfa9933faed563c5b291e4ef4536ce8732732e93288157b260b9" } } ], "extra": [ 1, 58, 151, 145, 101, 161, 76, 5, 184, 232, 67, 134, 140, 190, 217, 186, 160, 54, 212, 65, 114, 1, 172, 189, 16, 51, 180, 179, 16, 152, 122, 162, 149, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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