Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e1fbfc8545db81c4c363474c853c3e0c2f0c6d16ab7e14239c7a3331ee31090

Tx prefix hash: a95628615cbdfe1b82b80c4947c09448b4ae9673ff092ea79bd95d230e727158
Tx public key: 5c449e238285a36e4aa542cf8791c6bd82fcb0a99518f0aba323e22cdbf6b61d
Timestamp: 1693357960 Timestamp [UCT]: 2023-08-30 01:12:40 Age [y:d:h:m:s]: 01:178:16:03:41
Block: 836855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388786 RingCT/type: yes/0
Extra: 015c449e238285a36e4aa542cf8791c6bd82fcb0a99518f0aba323e22cdbf6b61d0211000000046c3a21c3000000000000000000

1 output(s) for total of 1.035534680000 dcy

stealth address amount amount idx
00: 7dd29c4abf1fe334b2a8f6610d05838a80f44e8d96a32853c20379f826363e36 1.035534680000 1289455 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": 836865, "vin": [ { "gen": { "height": 836855 } } ], "vout": [ { "amount": 1035534680, "target": { "key": "7dd29c4abf1fe334b2a8f6610d05838a80f44e8d96a32853c20379f826363e36" } } ], "extra": [ 1, 92, 68, 158, 35, 130, 133, 163, 110, 74, 165, 66, 207, 135, 145, 198, 189, 130, 252, 176, 169, 149, 24, 240, 171, 163, 35, 226, 44, 219, 246, 182, 29, 2, 17, 0, 0, 0, 4, 108, 58, 33, 195, 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