Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9031e74d0142396757639cafaa94aa148b1729182a6bb21bac9e1f23eb4dfb7

Tx prefix hash: 6fba796d5563e798049a432ba251821aa88c526a1f9096377340b5903de7c384
Tx public key: a03fd7ac21c2fe4c02f4ed225e38b85cdb87d918c5f0b956d5d49c7a8513853b
Timestamp: 1745689173 Timestamp [UCT]: 2025-04-26 17:39:33 Age [y:d:h:m:s]: 00:213:22:44:12
Block: 1270022 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150638 RingCT/type: yes/0
Extra: 01a03fd7ac21c2fe4c02f4ed225e38b85cdb87d918c5f0b956d5d49c7a8513853b02110000000cf7011ad5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9897f4e5c763039af49f4b109f7bba16923f4e5cd1ab5008258a32ae7148cc7 0.600000000000 1757263 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": 1270032, "vin": [ { "gen": { "height": 1270022 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9897f4e5c763039af49f4b109f7bba16923f4e5cd1ab5008258a32ae7148cc7" } } ], "extra": [ 1, 160, 63, 215, 172, 33, 194, 254, 76, 2, 244, 237, 34, 94, 56, 184, 92, 219, 135, 217, 24, 197, 240, 185, 86, 213, 212, 156, 122, 133, 19, 133, 59, 2, 17, 0, 0, 0, 12, 247, 1, 26, 213, 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