Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 271e88c2309261bd04a46c8bb787af2f912a5b3a28477f3fd63cec97c49f47cd

Tx prefix hash: 793f49a38dfdc9ff3412cd5da14a4ac2a25e45c8e6b26760d299231562eb0b79
Tx public key: 3a2e7ba54adcf8af1cfd7101c925d594c275c82c8150990547dba3c8489e8db2
Timestamp: 1757721771 Timestamp [UCT]: 2025-09-13 00:02:51 Age [y:d:h:m:s]: 00:113:10:44:03
Block: 1367166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81262 RingCT/type: yes/0
Extra: 013a2e7ba54adcf8af1cfd7101c925d594c275c82c8150990547dba3c8489e8db2021100000002ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4ddff5664fe61b2df74983671618db2e4ffd84eee741810f4a4b10371e9335b 0.600000000000 1855205 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": 1367176, "vin": [ { "gen": { "height": 1367166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4ddff5664fe61b2df74983671618db2e4ffd84eee741810f4a4b10371e9335b" } } ], "extra": [ 1, 58, 46, 123, 165, 74, 220, 248, 175, 28, 253, 113, 1, 201, 37, 213, 148, 194, 117, 200, 44, 129, 80, 153, 5, 71, 219, 163, 200, 72, 158, 141, 178, 2, 17, 0, 0, 0, 2, 173, 121, 72, 208, 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