Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c1a95c9cdf628b1f5afe6d39cad7d237380b017acc24ad2123f4a2db21caad8

Tx prefix hash: 70703f4de3dd90423b6bf3ea1653c8ddd24146a5b4bd12ffdabe8ff2e972c1a8
Tx public key: 225289f22bc75d4089b24bd985d006028bbc158d154312a1f08c2a876eb74e67
Timestamp: 1740632811 Timestamp [UCT]: 2025-02-27 05:06:51 Age [y:d:h:m:s]: 00:315:14:36:15
Block: 1228143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223409 RingCT/type: yes/0
Extra: 01225289f22bc75d4089b24bd985d006028bbc158d154312a1f08c2a876eb74e6702110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a84e1278e447b1f2e697bdabb39ae4f8187daea7c421d3f263b92a567b29f690 0.600000000000 1715020 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": 1228153, "vin": [ { "gen": { "height": 1228143 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a84e1278e447b1f2e697bdabb39ae4f8187daea7c421d3f263b92a567b29f690" } } ], "extra": [ 1, 34, 82, 137, 242, 43, 199, 93, 64, 137, 178, 75, 217, 133, 208, 6, 2, 139, 188, 21, 141, 21, 67, 18, 161, 240, 140, 42, 135, 110, 183, 78, 103, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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