Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d13610c4465ee146ad8c88ea90cd717666308b9689814000542863e671e8ac69

Tx prefix hash: 9c2e1abeacce43537b71ffb68b2bbcfcde3163797b4fb9b976267c68e5ddbf9e
Tx public key: 40eae7240777ba40403c29603329e2a5a7d453d281bae6f5d63b3b428b207763
Timestamp: 1672965649 Timestamp [UCT]: 2023-01-06 00:40:49 Age [y:d:h:m:s]: 01:331:19:47:53
Block: 668481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498178 RingCT/type: yes/0
Extra: 0140eae7240777ba40403c29603329e2a5a7d453d281bae6f5d63b3b428b20776302110000000133af99f4000000000000000000

1 output(s) for total of 3.741492740000 dcy

stealth address amount amount idx
00: 2ddaa2878d1cd310662ce4b6fb4adf9fa0f6e85b1f357fdf7124e344c62791b6 3.741492740000 1109732 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": 668491, "vin": [ { "gen": { "height": 668481 } } ], "vout": [ { "amount": 3741492740, "target": { "key": "2ddaa2878d1cd310662ce4b6fb4adf9fa0f6e85b1f357fdf7124e344c62791b6" } } ], "extra": [ 1, 64, 234, 231, 36, 7, 119, 186, 64, 64, 60, 41, 96, 51, 41, 226, 165, 167, 212, 83, 210, 129, 186, 230, 245, 214, 59, 59, 66, 139, 32, 119, 99, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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