Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fb08df8919ac65d3e8800235d07e5f9f493c1a2d531d87fa81c956fdf7a1ce5

Tx prefix hash: 163f255b6e1d5ccae3de8dfed83f946063e14d27647e2c0fc6fa814f4149effc
Tx public key: 5c36e07200f5527d4d5f4db52d38d85733cb5bd998e9aed22dfd2691850c59e4
Timestamp: 1578005273 Timestamp [UCT]: 2020-01-02 22:47:53 Age [y:d:h:m:s]: 05:005:10:26:05
Block: 37464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1153902 RingCT/type: yes/0
Extra: 015c36e07200f5527d4d5f4db52d38d85733cb5bd998e9aed22dfd2691850c59e4021100000003d81c26c0000000000000000000

1 output(s) for total of 461.176392004000 dcy

stealth address amount amount idx
00: a1c75707ce4123f26cf5c4c7c2193bf63caae109f62d786c60666587663122cb 461.176392004000 63610 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": 37474, "vin": [ { "gen": { "height": 37464 } } ], "vout": [ { "amount": 461176392004, "target": { "key": "a1c75707ce4123f26cf5c4c7c2193bf63caae109f62d786c60666587663122cb" } } ], "extra": [ 1, 92, 54, 224, 114, 0, 245, 82, 125, 77, 95, 77, 181, 45, 56, 216, 87, 51, 203, 91, 217, 152, 233, 174, 210, 45, 253, 38, 145, 133, 12, 89, 228, 2, 17, 0, 0, 0, 3, 216, 28, 38, 192, 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