Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab449e64abe593f17b473698daccd792d77e9ae4f6fe199a85e5f2872c20b6f8

Tx prefix hash: 721c5451f53bb925b6a67e0e72553e34c157989ab0b8af95a0ba67a9ef48d95c
Tx public key: 88f258d84622bebf9d351d4636351e94e3b5a0d1f67da7437f77af22edce9441
Timestamp: 1671969412 Timestamp [UCT]: 2022-12-25 11:56:52 Age [y:d:h:m:s]: 02:314:19:26:30
Block: 660233 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 744400 RingCT/type: yes/0
Extra: 0188f258d84622bebf9d351d4636351e94e3b5a0d1f67da7437f77af22edce94410211000000047e406890000000000000000000

1 output(s) for total of 3.984501244000 dcy

stealth address amount amount idx
00: fe49af3f4bf054cf3190ae4882cdd5b1381c2592f22d24501fdf60e329fd14c6 3.984501244000 1100964 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": 660243, "vin": [ { "gen": { "height": 660233 } } ], "vout": [ { "amount": 3984501244, "target": { "key": "fe49af3f4bf054cf3190ae4882cdd5b1381c2592f22d24501fdf60e329fd14c6" } } ], "extra": [ 1, 136, 242, 88, 216, 70, 34, 190, 191, 157, 53, 29, 70, 54, 53, 30, 148, 227, 181, 160, 209, 246, 125, 167, 67, 127, 119, 175, 34, 237, 206, 148, 65, 2, 17, 0, 0, 0, 4, 126, 64, 104, 144, 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