Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcfaa165cc489200b3025d94ef8f31f1ee16a4cf048858c26ecbbe523756500c

Tx prefix hash: 4ca06919c27e6a07288ac5c8aa71343f1a65ea3b0064ae9eecb641c847cfe36a
Tx public key: f1cf8cfdea618116584cc654a96afedbb28b4e0be38a170a6cbfaa7d48f647e9
Timestamp: 1750254741 Timestamp [UCT]: 2025-06-18 13:52:21 Age [y:d:h:m:s]: 00:153:19:45:56
Block: 1307689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107743 RingCT/type: yes/0
Extra: 01f1cf8cfdea618116584cc654a96afedbb28b4e0be38a170a6cbfaa7d48f647e9021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd7f4fcf72abeddbadb9acd34c64a9797ea717c0ea54e39fb7f982e571335933 0.600000000000 1795300 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": 1307699, "vin": [ { "gen": { "height": 1307689 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd7f4fcf72abeddbadb9acd34c64a9797ea717c0ea54e39fb7f982e571335933" } } ], "extra": [ 1, 241, 207, 140, 253, 234, 97, 129, 22, 88, 76, 198, 84, 169, 106, 254, 219, 178, 139, 78, 11, 227, 138, 23, 10, 108, 191, 170, 125, 72, 246, 71, 233, 2, 17, 0, 0, 0, 1, 191, 81, 178, 162, 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