Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3479feb988371d7f0da0df6ec34de7bda04f70b10a8e2c81ec510b1a26e35c8b

Tx prefix hash: a92262161f68cd2d7b67181ed8c65654670884cecad073d991760be753ecc951
Tx public key: d5ea3872de451241e66d4ddc9a5a7896c4632b60f8080bcb212461839d4cf64c
Timestamp: 1723888487 Timestamp [UCT]: 2024-08-17 09:54:47 Age [y:d:h:m:s]: 00:255:05:46:48
Block: 1089804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182311 RingCT/type: yes/0
Extra: 01d5ea3872de451241e66d4ddc9a5a7896c4632b60f8080bcb212461839d4cf64c02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5484ee193cc405054333f5869a999f3aa3447c7e0cc838c9ea24adfcfeb88503 0.600000000000 1564427 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": 1089814, "vin": [ { "gen": { "height": 1089804 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5484ee193cc405054333f5869a999f3aa3447c7e0cc838c9ea24adfcfeb88503" } } ], "extra": [ 1, 213, 234, 56, 114, 222, 69, 18, 65, 230, 109, 77, 220, 154, 90, 120, 150, 196, 99, 43, 96, 248, 8, 11, 203, 33, 36, 97, 131, 157, 76, 246, 76, 2, 17, 0, 0, 0, 3, 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