Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ac28fface418edc628b700d032a21cf8bba6e2940884318049fde17ca216a51

Tx prefix hash: 74d932e1696bb912d1fde03c85f4fd2c7f56a25f843bc1bfd830d5d9a148998a
Tx public key: 830d695db5dd9e5e4beed16dccc7f8989dd7c9623ffc1afa1a39ddae3c0dfda6
Timestamp: 1730084977 Timestamp [UCT]: 2024-10-28 03:09:37 Age [y:d:h:m:s]: 00:088:11:29:06
Block: 1141101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63247 RingCT/type: yes/0
Extra: 01830d695db5dd9e5e4beed16dccc7f8989dd7c9623ffc1afa1a39ddae3c0dfda60211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e21be489bbda9fe16d6930645a21e42e81dd839ce0aee1217ca56af44f46d68a 0.600000000000 1624908 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": 1141111, "vin": [ { "gen": { "height": 1141101 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e21be489bbda9fe16d6930645a21e42e81dd839ce0aee1217ca56af44f46d68a" } } ], "extra": [ 1, 131, 13, 105, 93, 181, 221, 158, 94, 75, 238, 209, 109, 204, 199, 248, 152, 157, 215, 201, 98, 63, 252, 26, 250, 26, 57, 221, 174, 60, 13, 253, 166, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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