Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85bd911156e72a7f4397381890ebd1d11a393357b8089a6172f70cf375116c6d

Tx prefix hash: fae609c021dca2befb90850ee20183804aadf0affeb72df10ab40e13bb396433
Tx public key: d0f0e894461ae94c1cd7f094052ff8b1285e305b057904a82a816b86f7bc05c4
Timestamp: 1578542916 Timestamp [UCT]: 2020-01-09 04:08:36 Age [y:d:h:m:s]: 05:065:20:48:43
Block: 41757 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1197021 RingCT/type: yes/0
Extra: 01d0f0e894461ae94c1cd7f094052ff8b1285e305b057904a82a816b86f7bc05c402110000000c4943cd9f000000000000000000

1 output(s) for total of 446.316116893000 dcy

stealth address amount amount idx
00: 8aff196a237c7d4cf0a9c2f1af526978d3a3bbc5d4632d4554a16e6194550fdd 446.316116893000 74729 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": 41767, "vin": [ { "gen": { "height": 41757 } } ], "vout": [ { "amount": 446316116893, "target": { "key": "8aff196a237c7d4cf0a9c2f1af526978d3a3bbc5d4632d4554a16e6194550fdd" } } ], "extra": [ 1, 208, 240, 232, 148, 70, 26, 233, 76, 28, 215, 240, 148, 5, 47, 248, 177, 40, 94, 48, 91, 5, 121, 4, 168, 42, 129, 107, 134, 247, 188, 5, 196, 2, 17, 0, 0, 0, 12, 73, 67, 205, 159, 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