Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7bf134d8d1c6b61c76deb79ffecf718f8b62e25ab248fbf5f8f15552a0813873

Tx prefix hash: dfd5ec6d5bf4f937996069bd08eaacf35fdc6d0d204fce2c3583c38cc42e598d
Tx public key: 03f56f8d463626e448741a6aeb9fb8e7e64f61cde53faa29546992e826a9550d
Timestamp: 1736538454 Timestamp [UCT]: 2025-01-10 19:47:34 Age [y:d:h:m:s]: 00:097:11:30:41
Block: 1194528 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69459 RingCT/type: yes/0
Extra: 0103f56f8d463626e448741a6aeb9fb8e7e64f61cde53faa29546992e826a9550d021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63c08d6f8b0563d46038a80bd5ac6876713b72e8393327df56e80c5da1140468 0.600000000000 1681101 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": 1194538, "vin": [ { "gen": { "height": 1194528 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63c08d6f8b0563d46038a80bd5ac6876713b72e8393327df56e80c5da1140468" } } ], "extra": [ 1, 3, 245, 111, 141, 70, 54, 38, 228, 72, 116, 26, 106, 235, 159, 184, 231, 230, 79, 97, 205, 229, 63, 170, 41, 84, 105, 146, 232, 38, 169, 85, 13, 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