Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ac2c4d0423cb71314cf633ba97674b9940466e7872a3e93da52980a4c45535a

Tx prefix hash: a853c17a2d4e8da059f67934c9173db92ba60b9ca39a3e259b9f6009120c15c2
Tx public key: ced0fca66dae0a7c2369a6cb5a48bc95333d243bb82e4efb7343fc75141c7258
Timestamp: 1677487906 Timestamp [UCT]: 2023-02-27 08:51:46 Age [y:d:h:m:s]: 02:091:19:17:25
Block: 705985 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 587246 RingCT/type: yes/0
Extra: 01ced0fca66dae0a7c2369a6cb5a48bc95333d243bb82e4efb7343fc75141c725802110000000183600029000000000000000000

1 output(s) for total of 2.810467265000 dcy

stealth address amount amount idx
00: 65f811311399cde2627f9a35b35befefd1d98ccdcfa8f600b8f163977470e7ae 2.810467265000 1149702 of 0

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": 705995, "vin": [ { "gen": { "height": 705985 } } ], "vout": [ { "amount": 2810467265, "target": { "key": "65f811311399cde2627f9a35b35befefd1d98ccdcfa8f600b8f163977470e7ae" } } ], "extra": [ 1, 206, 208, 252, 166, 109, 174, 10, 124, 35, 105, 166, 203, 90, 72, 188, 149, 51, 61, 36, 59, 184, 46, 78, 251, 115, 67, 252, 117, 20, 28, 114, 88, 2, 17, 0, 0, 0, 1, 131, 96, 0, 41, 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