Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e38c32bb898793d61811a3ceb71fea4e6f4c4f210cb3075e7d020203e0b25459

Tx prefix hash: a0f0486319d338592ed4ae52fadc7fff80f0274dfeb0e3a8b70b84cd206ffa12
Tx public key: 0cbd6559e2653c10d49b866e4ee19e7de06f5318628813bab9a5627d7f032198
Timestamp: 1733635630 Timestamp [UCT]: 2024-12-08 05:27:10 Age [y:d:h:m:s]: 00:102:10:39:48
Block: 1170503 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73023 RingCT/type: yes/0
Extra: 010cbd6559e2653c10d49b866e4ee19e7de06f5318628813bab9a5627d7f032198021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d3435db9dda4f1dd3b48c2237c325bf5bd6bcab7b4d73fbf98c2fd4ba76ee97 0.600000000000 1656234 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": 1170513, "vin": [ { "gen": { "height": 1170503 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d3435db9dda4f1dd3b48c2237c325bf5bd6bcab7b4d73fbf98c2fd4ba76ee97" } } ], "extra": [ 1, 12, 189, 101, 89, 226, 101, 60, 16, 212, 155, 134, 110, 78, 225, 158, 125, 224, 111, 83, 24, 98, 136, 19, 186, 185, 165, 98, 125, 127, 3, 33, 152, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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