Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c29cf1932b330ecc048c8a9790e143ffeb88f5697a1e7522c78714d66956919

Tx prefix hash: 3d69705fa4bb07930a759e4c3d3a393e6427da2af23b81e63a172f1f7dbb5a5f
Tx public key: 1a81a87505a1ea90be2937649d6e0f07be0058f6ed05b42adb9218d997e90e38
Timestamp: 1745866858 Timestamp [UCT]: 2025-04-28 19:00:58 Age [y:d:h:m:s]: 00:009:03:53:35
Block: 1271494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6547 RingCT/type: yes/0
Extra: 011a81a87505a1ea90be2937649d6e0f07be0058f6ed05b42adb9218d997e90e3802110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2e762c6a76c16ec2efb4d9804f55b7a307d2726b23e2be4eeee1bc65dbf79fc 0.600000000000 1758755 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": 1271504, "vin": [ { "gen": { "height": 1271494 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2e762c6a76c16ec2efb4d9804f55b7a307d2726b23e2be4eeee1bc65dbf79fc" } } ], "extra": [ 1, 26, 129, 168, 117, 5, 161, 234, 144, 190, 41, 55, 100, 157, 110, 15, 7, 190, 0, 88, 246, 237, 5, 180, 42, 219, 146, 24, 217, 151, 233, 14, 56, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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