Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0d346b368dcaebb132566225c27005c71d6975f4b13730bc1ed3292cf2ce988

Tx prefix hash: 4d1e003bc083580497ebd8432db76da461430ec3023bf6b75163fa3ae3786a1a
Tx public key: f818f1cb4b2a38fb146f8adc7ffb242a38223edc647240acc049c32d5e8c8c7b
Timestamp: 1579046952 Timestamp [UCT]: 2020-01-15 00:09:12 Age [y:d:h:m:s]: 04:316:20:20:10
Block: 45676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1115961 RingCT/type: yes/0
Extra: 01f818f1cb4b2a38fb146f8adc7ffb242a38223edc647240acc049c32d5e8c8c7b021100000023bd0f9f9f000000000000000000

1 output(s) for total of 433.168921991000 dcy

stealth address amount amount idx
00: 9e0c5ef384fd97e27250e5dc3fe1aea185d418ee84b2c82391cc96a7b11585b2 433.168921991000 83590 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": 45686, "vin": [ { "gen": { "height": 45676 } } ], "vout": [ { "amount": 433168921991, "target": { "key": "9e0c5ef384fd97e27250e5dc3fe1aea185d418ee84b2c82391cc96a7b11585b2" } } ], "extra": [ 1, 248, 24, 241, 203, 75, 42, 56, 251, 20, 111, 138, 220, 127, 251, 36, 42, 56, 34, 62, 220, 100, 114, 64, 172, 192, 73, 195, 45, 94, 140, 140, 123, 2, 17, 0, 0, 0, 35, 189, 15, 159, 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