Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed2b2795a0304d893ddfd1dff8a1159fb01ef316d5cec722280481f86b493761

Tx prefix hash: 3a94fba32d8a4655adabeb307b18eef843b8412d834640b0be8a33371eed2738
Tx public key: c92b54d5327e2b0a21b25af05e45b6a99097e2a122c39ad63e61a0f2f6e2a841
Timestamp: 1728649156 Timestamp [UCT]: 2024-10-11 12:19:16 Age [y:d:h:m:s]: 00:044:01:47:30
Block: 1129264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 31474 RingCT/type: yes/0
Extra: 01c92b54d5327e2b0a21b25af05e45b6a99097e2a122c39ad63e61a0f2f6e2a841021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ffcd0442476949d67150f981a58d507b5e23958a3a418f32e92b4aca49f22673 0.600000000000 1612089 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": 1129274, "vin": [ { "gen": { "height": 1129264 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ffcd0442476949d67150f981a58d507b5e23958a3a418f32e92b4aca49f22673" } } ], "extra": [ 1, 201, 43, 84, 213, 50, 126, 43, 10, 33, 178, 90, 240, 94, 69, 182, 169, 144, 151, 226, 161, 34, 195, 154, 214, 62, 97, 160, 242, 246, 226, 168, 65, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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