Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 014c2df8036e3b558c62c0a8fd169ae96361bc11b5db4b8b450453083a2e48ff

Tx prefix hash: b0d8f9a248c6209c9cdcd0af0358b3c09a1e15227f97dc835715e273ae33b74d
Tx public key: be36a60819afa0c538bf9c62144d5b6f0cfef723b18bc844325bdf629773e9ab
Timestamp: 1721515288 Timestamp [UCT]: 2024-07-20 22:41:28 Age [y:d:h:m:s]: 00:176:00:39:05
Block: 1070115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125943 RingCT/type: yes/0
Extra: 01be36a60819afa0c538bf9c62144d5b6f0cfef723b18bc844325bdf629773e9ab0211000000010cce0636000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65b5f05c4795096d1d31041e0bb2df826a8a2398c957fcf0a0403e19096686f3 0.600000000000 1541814 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": 1070125, "vin": [ { "gen": { "height": 1070115 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65b5f05c4795096d1d31041e0bb2df826a8a2398c957fcf0a0403e19096686f3" } } ], "extra": [ 1, 190, 54, 166, 8, 25, 175, 160, 197, 56, 191, 156, 98, 20, 77, 91, 111, 12, 254, 247, 35, 177, 139, 200, 68, 50, 91, 223, 98, 151, 115, 233, 171, 2, 17, 0, 0, 0, 1, 12, 206, 6, 54, 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