Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36907f10d47aa46f40754efa29fe7df72e27d6c89cf4426afa87d9339216860e

Tx prefix hash: e2e91513b76fab7ca5d43a528a061525461869b388ce56a10abfd1efdfdcc58a
Tx public key: f8dead8ae4a158f5d1b99069fe3842bf398aa91da70df2284eb1eda74c8113cf
Timestamp: 1685954907 Timestamp [UCT]: 2023-06-05 08:48:27 Age [y:d:h:m:s]: 01:310:17:07:55
Block: 775553 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 483262 RingCT/type: yes/0
Extra: 01f8dead8ae4a158f5d1b99069fe3842bf398aa91da70df2284eb1eda74c8113cf021100000006faf35c9c000000000000000000

1 output(s) for total of 1.652993437000 dcy

stealth address amount amount idx
00: 5eaab3484b21f958cf1654e3e7b2966d90fdf0f20b673983af5685f25b91f962 1.652993437000 1225070 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": 775563, "vin": [ { "gen": { "height": 775553 } } ], "vout": [ { "amount": 1652993437, "target": { "key": "5eaab3484b21f958cf1654e3e7b2966d90fdf0f20b673983af5685f25b91f962" } } ], "extra": [ 1, 248, 222, 173, 138, 228, 161, 88, 245, 209, 185, 144, 105, 254, 56, 66, 191, 57, 138, 169, 29, 167, 13, 242, 40, 78, 177, 237, 167, 76, 129, 19, 207, 2, 17, 0, 0, 0, 6, 250, 243, 92, 156, 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