Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8f230f66ab18ea212e96caf6c01bb21d50278519028de19bf90da38fe81d4fc

Tx prefix hash: c62257817ca4f6701742473c1c678fc2ab10f43c107b692ea6d50252e9d7288d
Tx public key: f9768cc8aa44cb13902b1237d8b91c45c055794ab17a823042f9c2cf6a70a739
Timestamp: 1737002658 Timestamp [UCT]: 2025-01-16 04:44:18 Age [y:d:h:m:s]: 00:156:07:10:57
Block: 1198366 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111372 RingCT/type: yes/0
Extra: 01f9768cc8aa44cb13902b1237d8b91c45c055794ab17a823042f9c2cf6a70a73902110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7df4f3f555a41fd7d8ae3f6d08cf5b565b90a5f5fbb18db09f50412bd80733a5 0.600000000000 1684989 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": 1198376, "vin": [ { "gen": { "height": 1198366 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7df4f3f555a41fd7d8ae3f6d08cf5b565b90a5f5fbb18db09f50412bd80733a5" } } ], "extra": [ 1, 249, 118, 140, 200, 170, 68, 203, 19, 144, 43, 18, 55, 216, 185, 28, 69, 192, 85, 121, 74, 177, 122, 130, 48, 66, 249, 194, 207, 106, 112, 167, 57, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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