Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4781aeb8402d37ba04c9679f02d24e09b9653454f0a76d235872371462bfa63f

Tx prefix hash: cc0a85fd97fa201bfdaafdc57f38b074dcf6febc217666de0c976e39f2ae5f1c
Tx public key: 657bc41d213e1e1f9ba894080539dc3fac7f7a335454660be9bda19ea7e88f27
Timestamp: 1580569121 Timestamp [UCT]: 2020-02-01 14:58:41 Age [y:d:h:m:s]: 05:008:08:35:25
Block: 56579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1157826 RingCT/type: yes/0
Extra: 01657bc41d213e1e1f9ba894080539dc3fac7f7a335454660be9bda19ea7e88f270211000000012264afe6000000000000000000

1 output(s) for total of 398.605593308000 dcy

stealth address amount amount idx
00: 7d901522e43737b918fc119323d001031647e0934a4e5c20fef07ca640e370ab 398.605593308000 104338 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": 56589, "vin": [ { "gen": { "height": 56579 } } ], "vout": [ { "amount": 398605593308, "target": { "key": "7d901522e43737b918fc119323d001031647e0934a4e5c20fef07ca640e370ab" } } ], "extra": [ 1, 101, 123, 196, 29, 33, 62, 30, 31, 155, 168, 148, 8, 5, 57, 220, 63, 172, 127, 122, 51, 84, 84, 102, 11, 233, 189, 161, 158, 167, 232, 143, 39, 2, 17, 0, 0, 0, 1, 34, 100, 175, 230, 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