Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc462e29f4b94ed231d5f89533c30f7ffdfa97176f0bd9ec3cb6a3253b380993

Tx prefix hash: 441f104612420259c305e39f2448f751a71cb6ff6b1aa302303938e0b60f75de
Tx public key: fcc619346bd612e04f17517688bb4f51d7678dc0f02109609415fd43151f268e
Timestamp: 1585418557 Timestamp [UCT]: 2020-03-28 18:02:37 Age [y:d:h:m:s]: 04:310:19:54:37
Block: 89065 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1120751 RingCT/type: yes/0
Extra: 01fcc619346bd612e04f17517688bb4f51d7678dc0f02109609415fd43151f268e02110000000445705818000000000000000000

1 output(s) for total of 311.093873910000 dcy

stealth address amount amount idx
00: 7dea58b104152cdeee7d79e7bdd214b365cbf8705d5fcc3ad0f1f8b52559c1b3 311.093873910000 159925 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": 89075, "vin": [ { "gen": { "height": 89065 } } ], "vout": [ { "amount": 311093873910, "target": { "key": "7dea58b104152cdeee7d79e7bdd214b365cbf8705d5fcc3ad0f1f8b52559c1b3" } } ], "extra": [ 1, 252, 198, 25, 52, 107, 214, 18, 224, 79, 23, 81, 118, 136, 187, 79, 81, 215, 103, 141, 192, 240, 33, 9, 96, 148, 21, 253, 67, 21, 31, 38, 142, 2, 17, 0, 0, 0, 4, 69, 112, 88, 24, 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