Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb1f61e3bc2e894231a51424a6370aff5000d7e35bf863e3704f4efcfc2c386e

Tx prefix hash: 45134af1dc0e9acea7584193d51b172167a270de5afff6e204f7a7ea431f40b2
Tx public key: dad38c0912ef4b8bc089604aa9491c1376e51ce3fd6975dcbdfb7b25e1fd027f
Timestamp: 1702074611 Timestamp [UCT]: 2023-12-08 22:30:11 Age [y:d:h:m:s]: 01:156:06:00:49
Block: 908939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372841 RingCT/type: yes/0
Extra: 01dad38c0912ef4b8bc089604aa9491c1376e51ce3fd6975dcbdfb7b25e1fd027f021100000003e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8840dbe381415e29a3f371cef1218c45926efe28a61e98104ca09690bd1e7b63 0.600000000000 1366002 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": 908949, "vin": [ { "gen": { "height": 908939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8840dbe381415e29a3f371cef1218c45926efe28a61e98104ca09690bd1e7b63" } } ], "extra": [ 1, 218, 211, 140, 9, 18, 239, 75, 139, 192, 137, 96, 74, 169, 73, 28, 19, 118, 229, 28, 227, 253, 105, 117, 220, 189, 251, 123, 37, 225, 253, 2, 127, 2, 17, 0, 0, 0, 3, 224, 133, 50, 182, 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