Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f4e3f8bad75fa70f800134e7fb61f2dfcf799578b654870d76039a584f96a4c

Tx prefix hash: 19bd927e7bbaca70f2b8386dc719c88a542a0f53d18cb146e4177985e5d56c5f
Tx public key: a7b7a652c177d05eb39935f1cf489a7c677593f17ae5fa5a27af7ce71d3badc3
Timestamp: 1724515598 Timestamp [UCT]: 2024-08-24 16:06:38 Age [y:d:h:m:s]: 00:226:03:06:12
Block: 1095021 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161438 RingCT/type: yes/0
Extra: 01a7b7a652c177d05eb39935f1cf489a7c677593f17ae5fa5a27af7ce71d3badc3021100000001e337358e000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0dd141b44a5d0d3474564f7a7348d709575d19fbe1777812ee533a250e239389 0.600000000000 1570150 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": 1095031, "vin": [ { "gen": { "height": 1095021 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0dd141b44a5d0d3474564f7a7348d709575d19fbe1777812ee533a250e239389" } } ], "extra": [ 1, 167, 183, 166, 82, 193, 119, 208, 94, 179, 153, 53, 241, 207, 72, 154, 124, 103, 117, 147, 241, 122, 229, 250, 90, 39, 175, 124, 231, 29, 59, 173, 195, 2, 17, 0, 0, 0, 1, 227, 55, 53, 142, 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