Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47a9eee8d8bc6ecd92efc7d6c4ab840f477e5351526661ea922f1b34c904d3ff

Tx prefix hash: 7683585c5b7fc9af6eca87ba9ff94968436d3e5d43aff6b71f2c2c21ba750222
Tx public key: 1a5fb5bb387cf6049f7db281942a436d2241db34a120f7c3694f1406eb2a9f50
Timestamp: 1730123073 Timestamp [UCT]: 2024-10-28 13:44:33 Age [y:d:h:m:s]: 00:138:15:42:37
Block: 1141408 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98930 RingCT/type: yes/0
Extra: 011a5fb5bb387cf6049f7db281942a436d2241db34a120f7c3694f1406eb2a9f5002110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 592335d7b6009a07249ef63bde4ce1fe883f4837d1bdaeea7e1d40bd9ebb3162 0.600000000000 1625215 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": 1141418, "vin": [ { "gen": { "height": 1141408 } } ], "vout": [ { "amount": 600000000, "target": { "key": "592335d7b6009a07249ef63bde4ce1fe883f4837d1bdaeea7e1d40bd9ebb3162" } } ], "extra": [ 1, 26, 95, 181, 187, 56, 124, 246, 4, 159, 125, 178, 129, 148, 42, 67, 109, 34, 65, 219, 52, 161, 32, 247, 195, 105, 79, 20, 6, 235, 42, 159, 80, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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