Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 101a96850981d752fc2b0660a1ae194fc208690660c0e464ae8118e8a16907bd

Tx prefix hash: ae36021da1555b63fe9ea58273cbc6d295ac47ff06b2d32c6d2e1ea4ca43b3da
Tx public key: 04c40d572495984809d380ba3114a18c83c11fd6d818ff137aeefa08a93a025f
Timestamp: 1685387128 Timestamp [UCT]: 2023-05-29 19:05:28 Age [y:d:h:m:s]: 01:270:15:56:34
Block: 770855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 454594 RingCT/type: yes/0
Extra: 0104c40d572495984809d380ba3114a18c83c11fd6d818ff137aeefa08a93a025f02110000000275e3f0e9000000000000000000

1 output(s) for total of 1.713316354000 dcy

stealth address amount amount idx
00: 4b7ead302f2e9a08eae6446ccf19c1339d44b14db08ac46a5ffcfa631ca65af0 1.713316354000 1220188 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": 770865, "vin": [ { "gen": { "height": 770855 } } ], "vout": [ { "amount": 1713316354, "target": { "key": "4b7ead302f2e9a08eae6446ccf19c1339d44b14db08ac46a5ffcfa631ca65af0" } } ], "extra": [ 1, 4, 196, 13, 87, 36, 149, 152, 72, 9, 211, 128, 186, 49, 20, 161, 140, 131, 193, 31, 214, 216, 24, 255, 19, 122, 238, 250, 8, 169, 58, 2, 95, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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