Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 971bfc5f101eff98cfbb53e7c0cc8dac145ed3c5f80a51a6953dc9607eb5b9c4

Tx prefix hash: 4da9a8dbbf3d9eb0d3cce50f2aa2cbeb2c74d365bb867c220e876d647706d51d
Tx public key: 65426d18644017c1cecc849c080fe64739600cdd200c3b22358a5e31923432d8
Timestamp: 1583091919 Timestamp [UCT]: 2020-03-01 19:45:19 Age [y:d:h:m:s]: 05:248:06:24:35
Block: 74948 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1329525 RingCT/type: yes/0
Extra: 0165426d18644017c1cecc849c080fe64739600cdd200c3b22358a5e31923432d8021100000045c71d3ff9000000000000000000

1 output(s) for total of 346.471056966000 dcy

stealth address amount amount idx
00: 27f3775221d476ddf2561a69b6518a3617d049656f5ae80917cb6acf13f7e1ab 346.471056966000 138562 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": 74958, "vin": [ { "gen": { "height": 74948 } } ], "vout": [ { "amount": 346471056966, "target": { "key": "27f3775221d476ddf2561a69b6518a3617d049656f5ae80917cb6acf13f7e1ab" } } ], "extra": [ 1, 101, 66, 109, 24, 100, 64, 23, 193, 206, 204, 132, 156, 8, 15, 230, 71, 57, 96, 12, 221, 32, 12, 59, 34, 53, 138, 94, 49, 146, 52, 50, 216, 2, 17, 0, 0, 0, 69, 199, 29, 63, 249, 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