Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a671ddf44cc5cfb0cd57eab14fca3fdc97ea74f2ddee78ad5656e855c186e36

Tx prefix hash: 8eeada360afdf6c1250f226374383a5ec7f5cf28338384e981d62d6c2b98d570
Tx public key: f89f780b8d961a01d822c9a63fbfb1ad3410a2aaa5db2d713f3f21c5ba66f674
Timestamp: 1673269417 Timestamp [UCT]: 2023-01-09 13:03:37 Age [y:d:h:m:s]: 02:004:18:34:09
Block: 670990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 525320 RingCT/type: yes/0
Extra: 01f89f780b8d961a01d822c9a63fbfb1ad3410a2aaa5db2d713f3f21c5ba66f67402110000000852542ceb000000000000000000

1 output(s) for total of 3.670553382000 dcy

stealth address amount amount idx
00: 7d1a4c0cd0e1443f2249d1a6feb3e5d7aeb3018750828ed7c86c2fa31bbd48b0 3.670553382000 1112443 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": 671000, "vin": [ { "gen": { "height": 670990 } } ], "vout": [ { "amount": 3670553382, "target": { "key": "7d1a4c0cd0e1443f2249d1a6feb3e5d7aeb3018750828ed7c86c2fa31bbd48b0" } } ], "extra": [ 1, 248, 159, 120, 11, 141, 150, 26, 1, 216, 34, 201, 166, 63, 191, 177, 173, 52, 16, 162, 170, 165, 219, 45, 113, 63, 63, 33, 197, 186, 102, 246, 116, 2, 17, 0, 0, 0, 8, 82, 84, 44, 235, 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