Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d81ddaa0e6b2f1d93abb7abe2d8882de902bb9c7f7cf668a50a3eb484185858d

Tx prefix hash: 353563953b7623494f3732c1c1f38c09a5c5280b0697f2832876415b534e4e82
Tx public key: 5bd9f66b46de85369094f5f630d163be0abc2251be547725db842d1226b37f32
Timestamp: 1577629445 Timestamp [UCT]: 2019-12-29 14:24:05 Age [y:d:h:m:s]: 05:043:07:27:58
Block: 34389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1180684 RingCT/type: yes/0
Extra: 015bd9f66b46de85369094f5f630d163be0abc2251be547725db842d1226b37f3202110000000d4ac5aa02000000000000000000

1 output(s) for total of 472.123723156000 dcy

stealth address amount amount idx
00: 16fb02e8b3cc3ef605d5b0467b59e43dc68e1239a19f2c482fa4e3853349b778 472.123723156000 57871 of 0

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": 34399, "vin": [ { "gen": { "height": 34389 } } ], "vout": [ { "amount": 472123723156, "target": { "key": "16fb02e8b3cc3ef605d5b0467b59e43dc68e1239a19f2c482fa4e3853349b778" } } ], "extra": [ 1, 91, 217, 246, 107, 70, 222, 133, 54, 144, 148, 245, 246, 48, 209, 99, 190, 10, 188, 34, 81, 190, 84, 119, 37, 219, 132, 45, 18, 38, 179, 127, 50, 2, 17, 0, 0, 0, 13, 74, 197, 170, 2, 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