Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ac4c13286d363316f64ab42a295f06d26ba9072b02aaa3f0151ad929b4c2fad

Tx prefix hash: 856d63d259e0b430528d9fb9b3dee9c8e69f7a5f6ca1d79a2bdeb05dae762562
Tx public key: b81c372fdada9480386529679101a9a6188de970c8f4c26ff23a39f52d3da846
Timestamp: 1754951594 Timestamp [UCT]: 2025-08-11 22:33:14 Age [y:d:h:m:s]: 00:106:15:03:17
Block: 1345078 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75489 RingCT/type: yes/0
Extra: 01b81c372fdada9480386529679101a9a6188de970c8f4c26ff23a39f52d3da846021100000003e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a77ab01a1f715eb7a4b3d1a5db904e7cb64549c6269880f49c3eebc8b3453a51 0.600000000000 1832967 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": 1345088, "vin": [ { "gen": { "height": 1345078 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a77ab01a1f715eb7a4b3d1a5db904e7cb64549c6269880f49c3eebc8b3453a51" } } ], "extra": [ 1, 184, 28, 55, 47, 218, 218, 148, 128, 56, 101, 41, 103, 145, 1, 169, 166, 24, 141, 233, 112, 200, 244, 194, 111, 242, 58, 57, 245, 45, 61, 168, 70, 2, 17, 0, 0, 0, 3, 228, 220, 144, 9, 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