Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3378fbb39849bf0a2c6381657256794bd9a9c64f2ed6e12f4111da11a4a52ba1

Tx prefix hash: 586c9fc0a6b3c959405908b724d78d297c0f4e03d8c90c85ac13539d23953fe9
Tx public key: 5e0374e162dd09666a2ae1f5e4bc111c65b965e671d527a1716a4f0aa2cbbdcf
Timestamp: 1720990131 Timestamp [UCT]: 2024-07-14 20:48:51 Age [y:d:h:m:s]: 00:289:16:34:58
Block: 1065774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206972 RingCT/type: yes/0
Extra: 015e0374e162dd09666a2ae1f5e4bc111c65b965e671d527a1716a4f0aa2cbbdcf02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61f38e5117fac9fc766f87417e4b5b697a2a331492d758df8b2f6125e5803305 0.600000000000 1536325 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": 1065784, "vin": [ { "gen": { "height": 1065774 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61f38e5117fac9fc766f87417e4b5b697a2a331492d758df8b2f6125e5803305" } } ], "extra": [ 1, 94, 3, 116, 225, 98, 221, 9, 102, 106, 42, 225, 245, 228, 188, 17, 28, 101, 185, 101, 230, 113, 213, 39, 161, 113, 106, 79, 10, 162, 203, 189, 207, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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