Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ac2dc22336990fa1c4781e495f0979254e3be5cc68200d4243cdd221c3fe3ab

Tx prefix hash: c421969df39b3cbb23da90354c2bc7896bbab2990d7b228793102aed79f9148e
Tx public key: e8f86721b17aa3d0f15d9c6ecc5265921654c95e1657b1740f8fce733e614bb8
Timestamp: 1739017447 Timestamp [UCT]: 2025-02-08 12:24:07 Age [y:d:h:m:s]: 00:357:23:37:17
Block: 1214790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253519 RingCT/type: yes/0
Extra: 01e8f86721b17aa3d0f15d9c6ecc5265921654c95e1657b1740f8fce733e614bb8021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b705d970f80f13e1a5e82087d644aecc1cc938a412b84b008f380a9e652e5b63 0.600000000000 1701585 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": 1214800, "vin": [ { "gen": { "height": 1214790 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b705d970f80f13e1a5e82087d644aecc1cc938a412b84b008f380a9e652e5b63" } } ], "extra": [ 1, 232, 248, 103, 33, 177, 122, 163, 208, 241, 93, 156, 110, 204, 82, 101, 146, 22, 84, 201, 94, 22, 87, 177, 116, 15, 143, 206, 115, 62, 97, 75, 184, 2, 17, 0, 0, 0, 5, 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