Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa7a69b1b4515a4efdf6c10d88936f86eff008c862344210f7d15fbdab23a5f2

Tx prefix hash: 361f9a1c87df2f6dfe70e8125242766b7550712b400aafa9d0e9312acabd5b80
Tx public key: 0dd4cef546684f7eeadd0dab4f1a2485602f00904ccd24e94178099a24b26fa6
Timestamp: 1644555181 Timestamp [UCT]: 2022-02-11 04:53:01 Age [y:d:h:m:s]: 02:316:02:49:33
Block: 436091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 745235 RingCT/type: yes/0
Extra: 010dd4cef546684f7eeadd0dab4f1a2485602f00904ccd24e94178099a24b26fa60211000000075eb576c5000000000000000000

1 output(s) for total of 22.031790141000 dcy

stealth address amount amount idx
00: 198b4f98672f752e0089ac95e0dc8a936fb2e43f77400b3db077af310d566f39 22.031790141000 847404 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": 436101, "vin": [ { "gen": { "height": 436091 } } ], "vout": [ { "amount": 22031790141, "target": { "key": "198b4f98672f752e0089ac95e0dc8a936fb2e43f77400b3db077af310d566f39" } } ], "extra": [ 1, 13, 212, 206, 245, 70, 104, 79, 126, 234, 221, 13, 171, 79, 26, 36, 133, 96, 47, 0, 144, 76, 205, 36, 233, 65, 120, 9, 154, 36, 178, 111, 166, 2, 17, 0, 0, 0, 7, 94, 181, 118, 197, 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