Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 135e61556a15594af628bc548b0185fca02f68fda3c5887f7ecd2286ea34f8ec

Tx prefix hash: f319b41d2f5cb3881b835e93c8aa6befca72efeb011918129d1ea7b56157256d
Tx public key: 1081a5c50ee025bf39505054f8a15c4c8439a01f64eae943f32d36dd1d072aab
Timestamp: 1585418587 Timestamp [UCT]: 2020-03-28 18:03:07 Age [y:d:h:m:s]: 05:221:11:37:28
Block: 89068 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1315513 RingCT/type: yes/0
Extra: 011081a5c50ee025bf39505054f8a15c4c8439a01f64eae943f32d36dd1d072aab02110000003d86362411000000000000000000

1 output(s) for total of 311.086753591000 dcy

stealth address amount amount idx
00: 2f0b3630aee61cad5ec9d7912bfef2dd96df9c1561a70b4920a673841114ac3d 311.086753591000 159932 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": 89078, "vin": [ { "gen": { "height": 89068 } } ], "vout": [ { "amount": 311086753591, "target": { "key": "2f0b3630aee61cad5ec9d7912bfef2dd96df9c1561a70b4920a673841114ac3d" } } ], "extra": [ 1, 16, 129, 165, 197, 14, 224, 37, 191, 57, 80, 80, 84, 248, 161, 92, 76, 132, 57, 160, 31, 100, 234, 233, 67, 243, 45, 54, 221, 29, 7, 42, 171, 2, 17, 0, 0, 0, 61, 134, 54, 36, 17, 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