Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85ff6675a56ff8722cac63986b7a24efcb2a767fb1673dedde391c691bfedea0

Tx prefix hash: dc17330b1e7dc787e6e2a97eafb644737ca7a6b63fe4a60c0beeb98d233267f6
Tx public key: 0c845a944c0ea6eedcae0d4bd27f7b7dd745da2a8306884dc7629979cf4f0188
Timestamp: 1723301194 Timestamp [UCT]: 2024-08-10 14:46:34 Age [y:d:h:m:s]: 01:085:15:45:46
Block: 1084925 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319683 RingCT/type: yes/0
Extra: 010c845a944c0ea6eedcae0d4bd27f7b7dd745da2a8306884dc7629979cf4f018802110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a406b5dc1cb1cd522927df86907594f6dc50d2ad697ec91308f87acc5864b5fc 0.600000000000 1559376 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": 1084935, "vin": [ { "gen": { "height": 1084925 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a406b5dc1cb1cd522927df86907594f6dc50d2ad697ec91308f87acc5864b5fc" } } ], "extra": [ 1, 12, 132, 90, 148, 76, 14, 166, 238, 220, 174, 13, 75, 210, 127, 123, 125, 215, 69, 218, 42, 131, 6, 136, 77, 199, 98, 153, 121, 207, 79, 1, 136, 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