Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 830d033d649d6fd64eafb1ef410ac58d3c422498d8de356248b7374b438691e3

Tx prefix hash: 2a58baf503cad2ab991f76fe3c48e3396f4f83fc21ceff1c1afc54b5e82b6615
Tx public key: 91d5e81218d2668ffd3316e2758be610ec5b5da09d78916b4bea7b19b6d6c04c
Timestamp: 1737543121 Timestamp [UCT]: 2025-01-22 10:52:01 Age [y:d:h:m:s]: 00:051:05:10:13
Block: 1202804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36428 RingCT/type: yes/0
Extra: 0191d5e81218d2668ffd3316e2758be610ec5b5da09d78916b4bea7b19b6d6c04c021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc5009a88925370dc4719eb14141a2e22eee006d012a766afe531aa441c66920 0.600000000000 1689471 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": 1202814, "vin": [ { "gen": { "height": 1202804 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc5009a88925370dc4719eb14141a2e22eee006d012a766afe531aa441c66920" } } ], "extra": [ 1, 145, 213, 232, 18, 24, 210, 102, 143, 253, 51, 22, 226, 117, 139, 230, 16, 236, 91, 93, 160, 157, 120, 145, 107, 75, 234, 123, 25, 182, 214, 192, 76, 2, 17, 0, 0, 0, 1, 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