Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c6018c77f8aca3c7be7f3dcfa362559711456ab8c5b1e18a4693bc75282d53d

Tx prefix hash: 4311078d44bc88407b4135b890a765e5b7fd39e2858a0f7948a1b09f4a58b890
Tx public key: 7ad976c68de57ccbb7982477e9fe1ebd4f7564b1e117e2114c0a523c01567510
Timestamp: 1578938891 Timestamp [UCT]: 2020-01-13 18:08:11 Age [y:d:h:m:s]: 05:136:01:22:48
Block: 44857 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1247391 RingCT/type: yes/0
Extra: 017ad976c68de57ccbb7982477e9fe1ebd4f7564b1e117e2114c0a523c015675100211000000164943cd9f000000000000000000

1 output(s) for total of 435.884051020000 dcy

stealth address amount amount idx
00: 79737641412cdc4ad5539eaef6bb810ee187214fca409f267a08419dd750281b 435.884051020000 81759 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": 44867, "vin": [ { "gen": { "height": 44857 } } ], "vout": [ { "amount": 435884051020, "target": { "key": "79737641412cdc4ad5539eaef6bb810ee187214fca409f267a08419dd750281b" } } ], "extra": [ 1, 122, 217, 118, 198, 141, 229, 124, 203, 183, 152, 36, 119, 233, 254, 30, 189, 79, 117, 100, 177, 225, 23, 226, 17, 76, 10, 82, 60, 1, 86, 117, 16, 2, 17, 0, 0, 0, 22, 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