Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af2be9a485d2ed5da4b67706da6fd1032bbc9192acdf3972b04a3deab1796bdf

Tx prefix hash: 04cf476f084c462c8bc16d3d2f2097ae706ce1ff4272a58ca039ec155cb93c4c
Tx public key: 81e3ef8e61ea5188fd21ab888748f08b0c19c64b46385386da46a8cf6aae8fe5
Timestamp: 1685495897 Timestamp [UCT]: 2023-05-31 01:18:17 Age [y:d:h:m:s]: 01:358:04:43:37
Block: 771756 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 517241 RingCT/type: yes/0
Extra: 0181e3ef8e61ea5188fd21ab888748f08b0c19c64b46385386da46a8cf6aae8fe5021100000001faf35c9c000000000000000000

1 output(s) for total of 1.701579216000 dcy

stealth address amount amount idx
00: c1d39136933ba11d763a5edc47342263d41594f989079cbaeb54dbdc9a37764c 1.701579216000 1221133 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": 771766, "vin": [ { "gen": { "height": 771756 } } ], "vout": [ { "amount": 1701579216, "target": { "key": "c1d39136933ba11d763a5edc47342263d41594f989079cbaeb54dbdc9a37764c" } } ], "extra": [ 1, 129, 227, 239, 142, 97, 234, 81, 136, 253, 33, 171, 136, 135, 72, 240, 139, 12, 25, 198, 75, 70, 56, 83, 134, 218, 70, 168, 207, 106, 174, 143, 229, 2, 17, 0, 0, 0, 1, 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